home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Gold Collection
/
Software Vault - The Gold Collection (American Databankers) (1993).ISO
/
cdr31
/
cdu_v210.zip
/
CDUDOCEN.DOC
< prev
next >
Wrap
Text File
|
1993-05-21
|
91KB
|
2,059 lines
╔══════════════════════════════ ┌─────────────────┐
║ CDU CATDISK <tm> │ D.I.S.P. │────┐
║ Utility package │ │░░░░│
╟────────────────────────────── │ │░░░░│
║ (c) 1993 Robert W.van Hoeven │ Dutch │░░░░│
╟────────────────────────────── │ Independent │░░░░│
║ Release : 2.10 │ ShareWare │░░░░│
║ Rel.Date: May, 20th, 1993 │ Programmer│░░░░│
╠══════════════════════════════ └─────────────────┘░░░░│
║ | │░░░░░░░░░░░░░░░░░│
║ │ CDC.EXE / CDM.EXE | └─────────────────┘
║ │ CDR.EXE / CDS.EXE | ┌─────┐ |
║ │ CDF.EXE / CDT.EXE | │░░░░░│ |
║ │ | └──┬──┘ |
║ │ Lines starting with '│' are | ┌────┴────┐ |
║ │ changes to release 1.32/2.01 ------││││││ ═══│-------
║ └─────────┘
╠═══════════════════════════════
║ Address: Robert W. van Hoeven
║ PO. Box 131
║ 1170 AC Badhoevedorp
║ Nederland / Holland
╚═══════════════════════════════
│┌─────────────────────────────────────────────────────────────────────┐
││ WARNING : THIS RELEASE OF CDU WILL ONLY WORK WITH CATDISK <TM> │
││ RELEASE 7.00 OR HIGHER. IF YOU USE A PRE 6.30 VERSION │
││ YOU MUST TRY TO FIND THE CDU 1.15 RELEASE AND 6.30 TO │
││ 6.37 USERS CAN USE THE CDU 2.01 RELEASE !!!!!!!!!!!!! │
│└─────────────────────────────────────────────────────────────────────┘
┌───────┬─────────────────────────────────────────────────────────────┐
│ 0 │ Table of contents │
└───────┴─────────────────────────────────────────────────────────────┘
1 ---- General information
1.1 Copyrights and License Agreement
1.2 Newer versions and contacting the author
2 ---- Package description and requirements
2.1 Preface
2.2 Requirements
2.3 History
2.5 Introduction & specs
3 ---- Installation description
3.1 Installation
3.2 The configuration file(s)
3.3 CTL options
3.3.1 GLOBAL options
3.3.2 Options for CDC
3.3.3 Options for CDF
3.3.4 Options for CDM
3.3.5 Options for CDR
3.3.6 Options for CDT
│ 3.3.7 Options for CDZ
4 ---- Runtime information
4.1 General program information
4.2 CDC
4.3 CDR
4.4 CDF
4.5 CDM
4.6 CDS
4.7 CDT
│ 4.8 CDZ
│ 4.9 Notes on tape support
5 ---- Version information and credits
5.1 The BETA-team
5.2 Credits
5.3 Version history
5.4 Copyright, Trademarks
┌───────┬─────────────────────────────────────────────────────────────┐
│ 1 │ General information │
└───────┴─────────────────────────────────────────────────────────────┘
1.1 Copyrights and License Agreement
────────────────────────────────────
- Users of the CDU-package must accept this disclaimer of warranty:
- The CDU-package is supplied as is. The author disclaims all
warranties, expressed or implied, including, without limitation, the
warranties of merchantability and of fitness for any purpose. The
author assumes no liability for damages, direct or consequential,
which may result from the use of the CDU-package;
- The CDU-package is a "shareware program" and is provided at no
charge to the user for evaluation. Feel free to share it with your
friends, but please do not give it away altered or as part of
another system. The essence of "user-supported" software is to
provide personal computer users with quality software without high
prices, and yet to provide incentive for programmers to continue to
develop new products.
- If you find this program useful and find that you are using and
continue the use of the CDU-package after a 30 days trial period,
you must register the CDU-package as described below;
- Non-commercial can get a license for the usage up to this release of
the CDU-package for a small amount of money. Look into the details
in REGISTER.CDU. Previous registered users will receive a big
reduction to upgrade to the newer versions. These users should look
into the details in UPGRADE.CDU. For Non-commercial users there is
a POSSIBILITY to submit to one of the special contracts as explained
in the file REGISTER.CDU.
- Commercial usage of CDU will cost somewhat more. Also, a so called
'closed' Bulletin Board System (a system where the user must pay
direct to the SysOp to get full access) is has to pay more than a
Non-commercial user. Both types of users should look into the
details in REGISTER.CDU;
- The registration of the CDU-package will license ONE copy for use on
any computer at any one time, as long as the usage confirms to the
type of registration you have done (so NON-commercial usage when you
have a non-commercial license);
- Anyone distributing the CDU-package for any kind of remuneration
must first contact the Author at the address above for
authorization.
- You are encouraged to pass a copy of the CDU-package along to
your friends for evaluation. Please encourage them to register
their copy if they find that they can use it;
- Support on CDU, when used in a non-commercial environment, is
available by means of written letters or by entering the inter-
national echomail area DISP;
- Problems and suggestions can be entered in the FidoNet <tm> Echomail
conference <tm> called DISP (international). Entering this echo does
not exclude you of the duty to register the CDU-package, though
users who evaluate the product can enter the echo for questions;
- The CDU-package, all programs, the documentation and support-files
is copyrighted 1990,93 by Robert W. van Hoeven, PO. Box 131,
Badhoevedorp 1170AC, Holland. All rights are reserved. You may copy
this package for backup purposes. Also you may copy and share
unmodified copies of the whole package, providing that the copyright
notice is reproduced and included on all copies.
Excluded from this statement are the support-files written by other
authors. Please refer to the documentation of these programs for
copyrights and license agreements;
- It is forbidden to modify, adapt, translate, reverse engineer,
decompile and/or disassemble the software in the CDU-package.
Patching the medium at places that carry the software is seen as a
program change and is also forbidden. It is forbidden to create a so
called 'bypass' to skip the original introduction screens and delay.
Also it is forbidden to use such a 'bypass' unless supplied by the
author (Robert W. van Hoeven) himself;
- Performing any of the illegal actions as stated in the previous
lines, is a theft and no fair play to the author and, more
important, to the registered users;
- Bulletin Board Systems that distribute the CDU package can convert
the WHOLE package to any archive-system they like but all original
files must be included in the new archive. The CDU-package on the
Bulletin Board can contain at the most 2 extra files. These files
can only be a commercial for that Bulletin Board and/or validation
data that is presented as a service to all users and shall have no
other functions;
- After the normal trial period of 30 days, you must register the
soft- ware (see REGISTER.CDU) or you must remove it from your PC;
- Comments, suggestions and bug reports are welcome and will be
answered as soon I have the time to do so. You can send me a letter
of leave a NetMail <tm> message named to Rob Van.hoeven (mind the
│ point) on node 2:281/904 (RA Support, Monster, Holland, SysOp is
Reinier de Groot). When you want to send me normal mail, address it
to: Robert W. van Hoeven, PO. Box 131, 1171 AC Badhoevedorp,
Holland; Also you can enter messages in the FidoNet <tm> DISP
Echomail <tm> area;
1.2 Newer versions and contacting the author
───────────────────────────────────────────────────────────────────────
The newest version of CDU is always available at the DISP-HQ on node
│2:281/904. CDU is also distributed thru a number of DISP support
nodes. There are three ways of obtaining newer versions of CDU:
- Logging on at DISP-HQ or a support node
Look into the file SUPPORT.CDU for a full list of support nodes;
- Logging on to a SDS node
CDU is distributed thru SDS/SDN, but only big minors (x.10, x.20 and
so on) and majors (14.01, 15.01 and so on) are submitted to the SDS
distribution point in Holland;
- Logging on to your own BBS;
Chances are, that you will find an older version (international
users) because it will take some time for the new version to 'bleed'
thru the net;
- Update service;
You can enter a special update service (read REGISTER.CDU).
If you think you have found problems in CDU, or in any other case, you
wish to contact the author, you can send me:
- A letter to the address you can find in the header of this file;
- A NetMail <tm> message to Rob Van.hoeven (please mind the point
│ between Van and Hoeven) at 2:281/904 or (better) 2:281/904.5;
- A Message in the FidoNet <tm> DISP echomail <tm> area;
┌───────┬─────────────────────────────────────────────────────────────┐
│ 2 │ Package description and requirements │
└───────┴─────────────────────────────────────────────────────────────┘
2.1 Preface
────────────────────────────────────────────────────────────────────────
Please notice the following:
- CDU is a ShareWare product in every right way, this means this
software is not crippled in any way;
- These programs only works when you work with the original CATDISK.EXE
program. CATDISK <tm> is (c) 1986-93 by Rick Hillier;
- This release of CDU works with CATDISK 6.3x and higher releases. The
older 6.2x and lower releases have a different database structure.
You can try to find CDU V 1.15 (that last release that supports this
format) or upgrade to the current version of CATDISK;
2.2 Requirements
────────────────────────────────────────────────────────────────────────
CDU requires: - PC XT/AT/386
- At least 200K free memory but it depends on the
options (picklist) you use;
- DOS 3.xx and higher;
(tested with 4Dos 3.02, should work with lower
versions). Tested with DOS 5.0;
- HDU optional
- The original CATDISK program (V 6.3x or higher);
2.3 History
────────────────────────────────────────────────────────────────────────
In the early '90 I got tired of my diskettes and their files. I needed
a diskette catalog program. I tried a few of them, including CATDISK
but all, also including CATDISK, seemed to slow for my VERY slow PC,
so I did write a small program myself that was nicer than most in-
memory catalog programs but did not include many options.
When I finally installed a new PC at home (a 386/33DX) and also hooked
│on as a co-sysop for 2:281/904, my files started to grow. Because I
more or less function as a remote backup for the BBS-files, my
collection raised from 50 360Kb diskettes to more than 200 720/1.44
diskettes, all containing archives.
I was surprised that I suddenly saw a new version of the CATDISK <tm>
program (4.60 it was), and decided to try it again. By now I have
created some 'small' customized programs that can help you with some
tasks in CATDISK <tm> that are not available or too specialized for
CATDISK <tm> to do.
These programs, though they can be better, do their jobs and are now
shared with you. The easiest thing you can do, is to delete them but
there could be one or more that suit your needs. In any case, if you
have comments or suggestions, let me know.
┌───────┬─────────────────────────────────────────────────────────────┐
│ 3 │ Installation description │
└───────┴─────────────────────────────────────────────────────────────┘
3.1 Installation
────────────────────────────────────────────────────────────────────────
The installation of the CDU package is very flexible. The first
release did not contain any options but the current (and newer
releases will).
The installation is as follows (suggested):
- Copy the *.EXE files you need (or all of them) to a directory in the
DOS-path;
- Create a line in AUTOEXEC.BAT where you set the environment variable
CATBASE. This variable must point to the directory that contains the
CATDISK.DTA/SUM files and/or any other CATDISK <tm> database(s) you
have. An example (where the CATDISK.DTA/SUM files are in C:\CAT). If
you will use a CDU.CTL or one or more specific xxx.CTL files, you can
leave out this step and use the CDUCATDISKBASE option in the CTL file
that you will use. An example when you want to add the SET command to
AUTOEXEC.BAT:
SET CATBASE=C:\CAT
- If you normally run CATDISK with special options (the /F[xxx] not
included, this option is inserted by some of the CDU programs
itself), you must create a line in your AUTOEXEC.BAT with the
following format:
SET CATDISK=[switch] {switch} .. {switch}
Where [switch]/{switch} are the command-line options you normally
use to start CATDISK. If normally you start CATDISK with /NC and
/NCC, the line should be 'SET CATDISK=/NC /NCC' (without the
quotes). The older CATPARM option (release 1.01) is now obsolete. It
is also possible to use different CATDISK-options for all different
│ databases you have. In this case, ignore the CATDISK switch and use
│ the BASEOPTIONS option in CDU.CTL;
- Be sure to have CATDISK.EXE somewhere in the DOS-path. All the CDU
programs will look for CATDISK.EXE in the DOS-path. If the program
does not reside in the DOS-PATH, you must add the CDUCATDISKPROG
option in the CDU.CTL or the separate xxx.CTL files;
- Create one or more configuration files for the CDU utilities (see
the next chapters);
- Previous releases contained a program CDD.EXE. This program could
not be called by that name when you run 4DOS <tm> on your system.
For this reason it is renamed to CDR.EXE. You should remove any
older CDD.EXE (from the CDU package!!) from your disk;
- If you are going to use CDZ, you need the Colorado (CMS) tape-backup
program TAPE.EXE. CDZ has been tested with the version 3.03 of this
program. Older and/or newer versions *could* not be complatible with
the layout of 3.03 and would cause CDZ to pass incorrect information
to CATDISK. It is advised to have TAPE.EXE somewhere in the DOS-path
and to use this path to call the program. If it is not, you can use
a special option in CDx.CTL (DOS-path access is advised though!);
3.2 The configuration file(s)
────────────────────────────────────────────────────────────────────────
All of the programs from the CDU package make usage of a control-file.
There are two options:
- You make one combines configuration file, called CDU.CTL. In this
configuration file you can put all the configuration options that
are common to all programs and also the program-specific options can
be put inside this file;
- You make one configuration file for each separate program. In this
case the configuration file is called ppp.CTL (where ppp is the name
of the program, f.i. CDT.CTL, CDM.CTL and so on);
The first option is the best. All options can be viewed in one file
and changes can be made easy !
The configuration file(s) is/are a normal ASCII-file(s) (text file(s))
you which can be created and edited with line-editors like EDLIN or
full screen editors like EDIT. You can make the file as big as you
like (by inserting many comment-lines) but remember that the size has
a relation with the speed of reading when a CDU program starts. Large
files will take the program to do longer over the startup.
The general formats of options are:
OPTION parameter parameter parameter .... parameter
or
[programname] OPTION parameter parameter parameter .... parameter
for active options, or:
% comment
for comments in the configuration file. In the documentation we call
the first parameter 'option' and the secondary parameters are called
'parameter'. For parameters, the following syntax is used in the
description:
[.....] this parameter is mandatory, it MUST be present and have a
valid value;
{.....} this parameter is optional. If it is NOT present, some
default is used;
'value' Values between quotes must be coded WITHOUT the quotes
itself UNLESS specified;
(*) If this mark occurs at the end of the options syntax, it
means that this option is used by other programs in the MTA
package as well. In that case refer to the bottom of the
description to see in which program(s) the option is used
also;
There are NO restrictions to the position you start the option, nor
the starting position of the parameters, but the 'option' and (if
present) the 'parameters' have to be separated with at least one or
more spaces. You can make any mixture of upper and lower case !
Some of the parameters in the CTL files can be overruled with
command-line switches. A generalized example of CDU.CTL is included in
the release-file. It contains ALL options available in this release.
One note about the two different formats of options (the 'OPTION ...'
and ['programname] OPTION ...' formats). Some options are SPECIFIC to
one of the programs in the CDU package (for example the GlobalChange
option which is only valid for CDT.EXE). When you use ONE combined
control-file (CDU.CTL), you must prefix the SPECIFIC options with the
name of the program they belong to. This is not needed when you create
separate control-files but it is still allowed. If an option is NOT
prefixed by a program-name, it is considered a GLOBAL option and thus
valid for all programs in the CDU package. This can cause errors when
you start a certain program. If you have a CDU.CTL and did not prefix
the GLOBALCHANGE option with CDT (for which it is needed), CDT will
work fine, but if you start CDM.EXE, it will terminate with an error
that reports an invalid option (GLOBALCHANGE). All programs in the CDU
package will FIRST look for a specific control-file (e.g. CDT.CTL or
CDM.CTL) and only when this file is NOT available, the program will
search for CDU.CTL. You can not put the GLOBAL options in CDU.CTL and
the specific options in a specific control-file. The programs will
only read ONE CTL-file, either the specific or the CDU.CTL file. In
the description of the options you can find if the option is GLOBAL
(for all CDU programs) or LOCAL (for a specific CDU program).
The following chapter will contain the various statements you can use
in the file.
3.3 CTL options
───────────────────────────────────────────────────────────────────────
The next chapters contain the options for all programs in the CDU
package.
3.3.1 GLOBAL options
───────────────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ RegistrationName [name] │
└─────────────────────────────────────────────────────────────────────┘
Usage : This option is only valid after you have registered the
package and received a key. For non-registered usage, this
statement must not be included. If you have specific
control-files, you must include this option in all of these
files !
┌─────────────────────────────────────────────────────────────────────┐
│ CDUTempDirectory [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : The various programs in the CDU package will create one or
more temporary files. Normally these are placed in the CURRENT
directory unless you specify THIS option.
[dir] Must point to a valid directory. The programs will test
if the directory is available and will abort if this is
not the case. You can use relative paths !
If you have specific control-files, you must include this
option in all of these files !
┌─────────────────────────────────────────────────────────────────────┐
│ CDUSwapDirectory [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Some of the programs in the CDU package will call CATDISK <tm>
itself. Before CATDISK <tm> is called, the program will first
swap itself from memory. This will go in the order XMS, EMS
and DISK. DISK is only used when there is not enough XMS or
EMS work-space available. When swapping to DISK, the program
will create a temporary file. This file will normally be
placed in the CURRENT directory unless this option is made
active.
[dir] Must point to a valid directory. The programs will test
if the directory is available and will abort if this is
not the case. You can use relative paths !
The programs will make a read-only (and hidden) swap-file.
When a program crashes (hangup), you must remove this file by
hand !
If you have specific control-files, you must include this
option in all of these files !
┌─────────────────────────────────────────────────────────────────────┐
│ CDUCatdiskProg [path] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally, the CDU utilities will search for CATDISK.EXE in the
DOS-path (some older versions even required that CATDISK.EXE
should be in the same directory as the CATDISK databases). If
CATDISK.EXE is NOT inside the DOS-path or the search in the
DOS-path is slow (XT and slow HDU's), you can add this option
that must point to the location AND name of CATDISK.EXE.
[path] Must point to the valid directory and file-name of the
CATDISK program.
If you have specific control-files, you must include this
option in all of these files !
┌─────────────────────────────────────────────────────────────────────┐
│ CDUCatdiskBase [dir] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Older versions of CDU used the CATBASE environment parameter
to locate the directory that contained the CATDISK database(s).
This will still work, but it is better to use this option in
the CDU.CTL (or specific xxx.CTL files) to point to the
directory that contains this (these) database(s).
[dir] Must point to the valid directory that contains the
CATDISK databases.
If you have specific control-files, you must include this
option in all of these files !
│┌─────────────────────────────────────────────────────────────────────┐
││ BaseOptions [base] [options] │
│└─────────────────────────────────────────────────────────────────────┘
│Usage : You can use different CATDISK <tm> options for all the databses
│ you have. For example, you have a database ARCH which contains
│ all archive file PLUS the in-archive files but you also have a
│ database GAME where you only log the archive files but NOT the
│ in-archive files. This can all be done with help of one or more
│ of the BASEOPTIONS options.
│
│ [base] Must be the name (without extension) of the CATDISK
│ database for which [options] will apply (for example
│ CATDISK, ARCH, GAMES and so on);
│
│ [options] These are the CATDISK <tm> options that apply for the
│ database [base]. Any space between options must be
│ coded as an underscore character, like NC_NCC;
│
│ For example you want archive directories (in-archive files) to
│ be stored for the ARCH database but not for the GAMES database.
│ The default extraction method you installed with CDISKCFG was
│ not to extract the archive directory. In CDx.CTL you can now
│ set:
│
│ BASEOPTIONS ARCH /ALLFILES
│
│ In which case /ALLFILES will be added as a command-line when
│ any of the CDU programs will call CATDISK for database ARCH !
│
│ You can use the BASEOPTIONS options to overcome the need for
│ a CATDISK environment variable. Be warned though that both
│ the CATDISK environment variable AND the options on the correct
│ BASEOPTIONS option will BOTH be passed to CATDISK whenever a
│ CDU program will call CATDISK !
│
│┌─────────────────────────────────────────────────────────────────────┐
││ BaseDrive [base] [drive] │
│└─────────────────────────────────────────────────────────────────────┘
│Usage : When you use different drives for different CATDISK catalogs
│ (for example, your ARCH database obtains the info from your
│ 3 1/2" A-drive and GAME needs the info from the 5 1/2" B-drive)
│ you can set the correct drive by using the /DRIVE= command-line
│ parameter. You can also connect databases to drives with the
│ BASEDRIVE options.
│
│ [base] Must be the name (without extension) of the CATDISK
│ database for which [drive] will apply (for example
│ CATDISK, ARCH, GAMES and so on);
│
│ [drive] This must be the drive-letter (without :) for the
│ drive that is always used when [base] is manipulated.
│
│ For CDM this option is duplicated in the DIRECTORY2BASE option.
│ Is this kept like this for compatibility reasons, but it is
│ advised to use the new BASEDRIVE option and not the assignment
│ in the DIRECTORY2BASE option for CDM.
3.3.2 Options for CDC
───────────────────────────────────────────────────────────────────────
CDC currently has NO specific options !
3.3.3 Options for CDF
───────────────────────────────────────────────────────────────────────
CDF currently has NO specific options !
3.3.4 Options for CDM
───────────────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ClusterSize [minsize] [maxsize] [clustersize] │
└─────────────────────────────────────────────────────────────────────┘
Usage : Normally, CDM will use a clustersize of 512 bytes for diskettes
with a high density and 1024 bytes for low density diskettes.
If you use specific cluster sizes or abnormal diskette formats,
you can supply up to 10 different formats with their cluster
sizes.
[minsize] The minimum available space (when formatted) for
this diskette format (like 1.400.000 for a 1.4
Mb diskette);
[maxsize] The maximum available space (when formatted) for
this diskette format (like 1.499.999 for a 1.4
Mb diskette);
[clustersize] The size of each cluster on diskettes that have
between [minsize] and [maxsize] bytes;
When you use normal formatting routines, you do not have to
supply any of this options.
┌─────────────────────────────────────────────────────────────────────┐
│ Directory2Base [dir] [base] {drive} │
└─────────────────────────────────────────────────────────────────────┘
Usage : CDM can move files from the harddisk to the diskettes.
Normally CDM will ask which CATDISK <tm> database has to used
and which drive will contain the diskettes (unless /BASE
and/or /DRIVE are supplied). In some configurations the user
uses a different approach. In these configurations, users
store the files for a SPECIFIC CATDISK <tm> database in a
SPECIFIC directory (for example, the files that will go to the
WIN3 CATDISK <tm> base will always be placed in F:\ZIP\WIN and
the files that go to the FSIM CATDISK <tm> base will always be
placed in the F:\ZIP\FSI directory). When this is the case in
your setup, you can use this option.
[dir] Must contain the name of the directory on harddisk
where the files for the SPECIFIC CATDISK <tm> base
[base] will be stored;
[base] Must contain the name (no extension) of the CATDISK
<tm> base where the files in directory [dir] on
harddisk will go to;
{drive} Can optionally contain the letter of the diskette
drive that must be used for the files that go to
│ CATDISK <tm> base [base] and are stored in [dir]. When
│ you want this (special) drive-setting to work with ALL
│ CDU-utilities, you can better specify one or more of
│ the BASEDRIVE options which (does) do the same but
│ works globally (e.g. for all CDU programs);
Based on the previous examples with WIN3 and FSIM, you could
code:
Directory2Base F:\ZIP\WIN WIN3 A
Directory2Base F:\ZIP\FSI FSIM B
The drives for WIN3 and FSIM are different in this case (WIN3
is put on the A-drive and FSIM uses another diskette format
on the B-drive).
After you have swapped to the correct directory (f.i. the
F:\ZIP\WIN directory) and CDM is started, CDM will detect
that the current directory (F:\ZIP\WIN) matches one of the
Directory2Base options and will move the files to the A:
drive and catalog them in the WIN3 CATDISK <tm> base.
If CDM can not find a match (so the current directory does
not match any of the Directory2Base options), CDM will ask
which database must be used (unless /BASE is supplied) and
which diskette-drive must be used (unless /DRIVE is
supplied).
3.3.5 Options for CDR
───────────────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ ToOldFiles [mmyy] │
│ ToOldFiles [-mm] │
└─────────────────────────────────────────────────────────────────────┘
Usage : CDR can (optionally) remove files based on the mask AND age.
When you want to remove selected files based on age, you can
supply the ToOldFiles option (or the /TOOLD= command-line
parameter). You can use only one of the two different formats.
The first format will decide the removal based on a fixed date
(month/year), the second format will decide based upon a
relative date ([current date] - [X-months]).
[mmyy] With this format, you supply the actual date which is
considered as to old. All files of this date and older
will be marked as to old. mm is the month (always 2
digits, 01-12) and yy is the year (always 2 digits,
80-99);
[-mm] With this format, you supply the number of months that
must be subtracted from the current date to create the
date that is considered as to old. The minus-sign is
mandatory and the number of months 'mm' can be
anything between 1 and 65534;
CDR can use the /TOOLD=- command-line switch (watch the minus
sign without a number) to switch the ToOldFIles option in the
control-file to OFF.
│┌─────────────────────────────────────────────────────────────────────┐
││ ExcludeFile [base] [mask] │
│└─────────────────────────────────────────────────────────────────────┘
│Usage : When you use CDR to clean your diskettes from files that are
│ old or need to be removed for some other reason, you will need
│ to enter 'N' (no) for each file that matches the criteria but
│ has a special meaning for you and must be kept on diskette.
│ For example, very special GIF's that you want to keep, one or
│ more utilities that never 'age' like archive-programs and so
│ on. To overcome the problem of entering 'N' for each of these
│ files EVERY time you run CDR (with the /TOOLD option or the
│ equivalent CDx.CTL option), you can exclude one or more of the
│ EXCLUDEFILE options. These options will work for ALL various
│ databases that you have or for just one (depending on the way
│ you code the option). If a file matches the criteria (mask
│ and/or the file is too old) but also matches one or more of
│ the EXCLUDEFILE options, the file will be shown on the screen
│ but can not be selected (it is skipped).
│
│ [base] This must be the name of the database for which the
│ exclusion will work. You must either code the full
│ name of the database (without extension, fi. ARCH and
│ NOT ARCH.DTA) or you must code an asterix ('*') in
│ which case this exclusion will work for ALL databases;
│
│ [mask] This must be a valid file-mask (wildcards are allowed)
│ which will be excluded by CDR. You can use the normal
│ DOS wildcards AND the special DISP-compatible '='
│ wildcard to do a shifting match (=TA will match mTA.exe
│ but also TAnd.zip, maTAhar.arc, test.dTA and so on);
│
│ The number of EXCLUDEFILE options per database is only limited
│ by the available conventional memory that is available when CDR
│ is running.
│
│ When you run CDR.EXE, you can exclude any new match on the fly
│ by using the 'E' answer. In that case CDR will add the new
│ entry (for the database you are working on) to the CDx.CTL file
│ which was used at the start of CDT.EXE. If there wasn't any
│ CDx.CRL file at startup, CDR.EXE will create a new one for you
│ and will signal you at the end of the run that the file has
│ been created !
│
│ Some examples. Given:
│
│ ExcludeFile * PK*.*
│ ExcludeFIle ARCH ARC*.*
│
│ Will exclude any match on PK*.* in ANY database and will also
│ exclude any match on ARC*.* in the ARCH database.
3.3.6 Options for CDT
───────────────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────────────┐
│ GlobalChange [from] [to] │
└─────────────────────────────────────────────────────────────────────┘
Usage : CDT can change text in the comment-file BEFORE it is passed to
CATDISK <tm>. This is needed most of the time. Most files you
have received are converted from one archive system to another
and when you download a comment-file from a BBS, it is
possible that the BBS uses ZIP and LZH as where you use ARJ
and already converted the LZH/ZIP file to ARJ. In this case
the file will be in the CATDISK <tm> database with .ARJ as the
extension and no match will be found if it is in the
comment-list with the .ZIP extension. GlobalChange (up to 100
of these options are allowed) can change one item to another
one.
[from] is the text in the comment-file you want to change. It
must be one continuous text and the match is depending
on the case;
[to] is the text that will replace the [from] text when a
match with [from] is made. If there are more matches on
one line (record) all matches are changed.
The function of GlobalChange is case sensitive ! When you are
not sure, include both the lower-case and upper-case values.
For example, change all known archive extensions into .ARJ:
GlobalChange .EXE .ARJ
GlobalChange .COM .ARJ
GlobalChange .ARC .ARJ
GlobalChange .LZH .ARJ
GlobalChange .LZS .ARJ
GlobalChange .HYP .ARJ
GlobalChange .SQZ .ARJ
GlobalChange .ZIP .ARJ
GlobalChange .ZOO .ARJ
GlobalChange .DWC .ARJ
GlobalChange .exe .ARJ
GlobalChange .com .ARJ
GlobalChange .arc .ARJ
GlobalChange .lzh .ARJ
GlobalChange .lzs .ARJ
GlobalChange .hyp .ARJ
GlobalChange .sqz .ARJ
GlobalChange .zip .ARJ
GlobalChange .zoo .ARJ
GlobalChange .dwc .ARJ
When you add the comment-file to more than one database (see
later), you don't have to be afraid that CDT will do too much
work. The changes to the comment-file are only made once and
this new file be passed to CATDISK <tm>. Also the original
file will not be changed !
┌─────────────────────────────────────────────────────────────────────┐
│ FileListUpdate [mask] [base] [sf] [ef] [sd] [ed] [sv] [ev] [sc] [ec]│
└─────────────────────────────────────────────────────────────────────┘
Usage : CDT must contain a in the comment-file BEFORE it is passed to
CDT is a nice utility if you get ALLFILES listings that will
be used to add comments to your CATDISK <tm> database(s). CDT
uses these option(s) as a table to know for which
comment-files, which databases must be updated and in what
manner.
[mask] This must be a valid DOS mask that matches one or more
comment-files (ALLFILES listings);
[base] This must be the name of the CATDISK <tm> database
(no extension) that must be updated with the comments
from this file;
[sf] This is the starting position of the filename in the
comment-file;
[ef] This is the ending position of the filename in the
comment-file;
[sd] This is the starting position of the directory in the
comment-file. Normally this is set to 0;
[ed] This is the ending position of the directory in the
comment-file. Normally this is set to 0;
[sv] This is the starting position of the volumeID in the
comment-file. Normally this is set to 0;
[ev] This is the ending position of the volumeID in the
comment-file. Normally this is set to 0;
[sc] This is the starting position of the comment in the
comment-file;
[ec] This is the ending position of the comment in the
comment-file;
An example to up update the CATDISK <tm> databases ARCH and
GAME with files with different format (examples CDT.EX1 and
CDT.EX2) is supplied inside the archive ! Also look inside the
example CDU.CTL file for a bigger example.
│3.3.7 Options for CDZ
│───────────────────────────────────────────────────────────────────────
│┌─────────────────────────────────────────────────────────────────────┐
││ TapeProgramPath [path] │
│└─────────────────────────────────────────────────────────────────────┘
│Usage : If you use CDZ, this program has to use TAPE.EXE from Colorado
│ (the Jumbo version, though the versions for other types from
│ this company could also work). CDZ has been tested with version
│ 3.03 of the Jumbo software (TAPE.EXE).
│
│ It is advised to have TAPE.EXE somewhere in the DOS-path and
│ let CDZ search for the program. If this is not your normal
│ setup, and/or you have renamed TAPE.EXE to another name, you
│ must supply this TAPEPROGRAMPATH option.
│
│ [path] must point to the drive, directory and filename of the
│ TAPE.EXE program (or the renamed version of it, if you
│ did rename TAPE.EXE to something else):
│
│ CDZ will call TAPE.EXE (or the equivalent) thru the DOS-shell
│ (COMMAND.COM or 4DOS.COM or alike file). To do so, it will use
│ the setting of the COMSPEC environment variable !
┌───────┬─────────────────────────────────────────────────────────────┐
│ 4 │ Runtime information │
└───────┴─────────────────────────────────────────────────────────────┘
4.1 General program description
────────────────────────────────────────────────────────────────────────
All programs described below work more or less the same. If you have
more than one CATDISK <tm> database, you can select to point to the
wanted database by means of a command-line switch (/BASE=) or by means
of a PICK-list. If you have more than one database and you do NOT sup-
ply the /BASE= parameter, the program will show a PICK-list with all
eligible databases. Just move the bar to the right database and hit
the [ENTER] button. All programs have some common command-line para-
meters that can be used. You can use /?, /H, ? or H to display the
valid command-line parameters for each of the programs.
All CDx programs that use a file-mask, contain one EXTRA mask that is
normally not available in DOS. The '=' mask can be used for a
'shifted' test. Some examples explain it best:
=RA will select tRAns.arc, RA_101.zip, warnRAm.arj and so on
=A.E will select mamA.Exe and so on;
You can not combine the '=' mask with other masks like ?? and ** !
4.2 CDC
────────────────────────────────────────────────────────────────────────
CDC is the smallest and easiest program. Sometimes the CATDISK <tm>
databases will contain 'garbage' characters in some fields. Though it
should be fixed, it is still possible that your databases contain
these characters. These characters do no harm but they can be a pain
in the neck in the case when you want to compress your CATDISK <tm>
database(s). If you use programs like DIET or the resident STACKER,
you can get some extra bytes of compression back when the fields in
the CATDISK <tm> databases are set to hex '00' for that part of the
│field that is NOT in use. This is also the case when your hard-disk is
│converted to a DOUBLESPACE disk.
CDC should be run once in a longer period and does nothing more than
cleaning all garbage in the CATDISK <tm> database. It should not al-
ter the active information but when you are unsure, you must backup
the database first.
CDC works with the following command-line options:
/BASE=nnnnnnnn You can use this parameter to point to the right
CATDISK <tm> database. [nnnnnnnn] is the name
(without extension) of the database. If there is only
one database, CDC will use it at once. If there are
more databases and you don't use this parameter, CDC
will show all possible databases and you can pick one
of them;
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
4.3 CDR
────────────────────────────────────────────────────────────────────────
CDR is a nifty utility that can help you to clean your diskette files.
CDR is the CATDISK <tm> delete utility. In general, you can use this
program in 2 ways.
- Normal delete (with extra mask)
You will start CDR with one or more file-masks to delete;
- Date-delete
You can delete files that are older than a certain month and year;
When CDR is started, it will search the database for all matches (you
can supply up to 50 ! masks) and will sort them on volume-ID after you
have been presented with a question if one or more (or even all) of
the matched files have to be deleted. Then CDR will ask you to mount
the first volume, the next volume and so on. CDR will combine all
files on one volume so you only have to mount diskettes only once.
They will be asked in volume-ID sorting order and only diskettes that
contain files to be deleted are asked for a mount.
After the file(s) are deleted for a specific volume, CDR will call
CATDISK <tm> and you can update the catalog with the original CATDISK
program.
CDR works with the following command-line options:
/BASE=nnnnnnnn the same as with CDC
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
/TOOLD=mmyy mmyy is a valid (4 digit) month and year. When you
supply this parameter, CDR will only delete files
that equal one of the masks AND are OLDER than the
supplied mmyy combination;
/TOOLD=-mmm The -mm format uses a relative date. In this case mm
months are subtracted from the current date and will
create the new date that is considered as the first
date that is to old. [mmm] can be anywhere between 1
and 65534 (far back in time, we then acted and looked
like monkeys);
/TOOLD=- This option is used to switch the ToOldFiles
option in either CDU.CTL or CDR.CTL to off;
/DRIVE=d CDR would like to know the drive that contains the
diskettes that are worked on (delete files). If you
do not supply the option, CDR will ask for the
drive-letter;
/NORESTART When you terminate CDR while CDR is busy with the
manipulation of diskettes (the second part), you can
start CDR again and it will go on as if nothing has
happened. Any selection screens are skipped and CDR
will go on with the next volume in the list. If this
is NOT what you want, you can supply /NORESTART and
CDR will start from scratch again. If you did finish
CDR in a NORMAL way (not pressing ESC), the restart
files are scratched and CDR will start from scratch
the next time. You can also force CDR to start from
scratch (after abnormal termination) by deleting the
files CDR$$???.??? from disk;
/MANUAL Normally CDR will start an automatic sequence to pass
the actions to CATDISK <tm>. This will work only
partial when you run a non-registered version of
CATDISK <tm>. In this case you can (must) add /MANUAL
to the command-line. The CDR program will NOT pass
the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS
command-line options to CATDISK <tm>, so you are on
your own when CATDISK <tm> is called;
4.4 CDF
────────────────────────────────────────────────────────────────────────
CDF looks much like CATDISK internal file-list but it is somewhat
faster and has some extra options. You can use the movement keys to
scroll left, right, up and down the list and you can use up to 50
masks in one run. Also the enhanced masks can be used ('='). One extra
option makes it possible to show the diskettes in free-space order so
you can easy select a diskette that can fit your new file(s).
CDF works with the following command-line options:
/BASE=nnnnnnnn the same as with CDC
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
/FREE Only show diskettes in free-space order
/ARC Display in-archive files also;
/ALL Search for file-mask in ALL available CATDISK <tm>
databases which are in the installed directory. CDF
will use ALL *.DTA files for the search.
/SD Sort the file-list on filedate (ascending). Within the
sorted list, files are sorted on filename.
/SV Sort the file-list on VolumeID (ascending). Within the
sorted list, files are sorted on filename.
/SA Sort the file-list on Archives (ascending). Within the
sorted list, files are sorted on filename.
/SS Sort the file-list on size (ascending). Within the
sorted list, files are sorted on filename.
4.5 CDM
────────────────────────────────────────────────────────────────────────
CDM is something you must try. Put all new files that have to go to
diskette into one directory on your harddisk (use separate directories
for files that will go into separate diskette-sets e.g. CATDISK <tm>
databases). Start CDM.
CDM will first try to look if older versions are already inside the
diskette collection (e.g. SCAN82 is on ARCHIVE 10 and now you have
SCAN83 ready to store on diskette).
For equal files, CDM will ask if you want to delete the file from
hard-disk (answer 'Y'). If you reply 'N', CDM will add the file to one
of the diskettes and BOTH (name-like) versions will reside on
diskette. If you answer 'A', CDM will remove the file from diskette
and will add the one from hard-disk to a new diskette !!
The algorithm to detect different versions is far from perfect. Only
files with names of 5 bytes or longer (excluding the extension) and
with the last 3 bytes unequal but the first bytes equal, are marked.
So, CT21 and CT53 are not detected but MTA_VE14 and MTA_VE16 are.
Now CDM will try to fit the new files on your diskettes in a way that
the diskettes are filled optimal.
This all will only use one mount per eligible diskette. After a
diskette is ready, CDM will call CATDISK so you can update the
database. CDM works at my place but not everybody will store files in
the way I do, so try before you use.
CDM works with the following command-line options:
│{directory-name} When you supply a (valid) directory-name in the
│ command-line options, CDM will start to work in THAT
│ directory and will also try to match THAT directory
│ with any DIRECTORY2BASE command that you may have
│ supplied;
/BASE=nnnnnnnn the same as with CDC
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
/DRIVE=d the same as with CDR
/NORESTART When you terminate CDM while CDM is busy with the
manipulation of diskettes (the second part), you can
start CDM again and it will go on as if nothing has
happened. Any selection screens are skipped and CDM
will go on with the next volume in the list. If this
is NOT what you want, you can supply /NORESTART and
CDM will start from scratch again. If you did finish
CDM in a NORMAL way (not pressing ESC), the restart
files are scratched and CDM will start from scratch
the next time. You can also force CDM to start from
scratch (after abnormal termination) by deleting the
files CDM$$???.??? from disk;
/MANUAL Normally CDM will start an automatic sequence to pass
the actions to CATDISK <tm>. This will work only
partial when you run a non-registered version of
CATDISK <tm>. In this case you can (must) add /MANUAL
to the command-line. The CDM program will NOT pass
the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS
command-line options to CATDISK <tm>, so you are on
your own when CATDISK <tm> is called;
4.6 CDS
────────────────────────────────────────────────────────────────────────
This is a nice utility if you get many request for copies of your
files. CDS will sort the files from new to old, will ask if you would
like to select each individual file and will show the number of bytes
you have selected. When you stop selecting files, CDS will start to
ask for diskettes and will copy files from the diskette to the current
directory. Also a FILES.BBS alike file, containing any comments from
the CATDISK <tm> database you selected, is copied onto the disk.
CDS works with the following command-line options:
/BASE=nnnnnnnn the same as with CDC
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
/DRIVE=d the same as with CDR
/DEL if supplied, CDS will not COPY the file from diskette
but will MOVE the file. In this case CATDISK <tm>
itself will be called to update the changed diskette
in the CATDISK <tm> database. With this option you
can select a set of files from a certain database,
move them to harddisk (also a FILES.BBS file is
created), use CDM to merge these files in a new
database and use CDT to update the comments from the
FILES.BBS file in this new database;
/NORESTART When you terminate CDS while CDS is busy with the
manipulation of diskettes (the second part), you can
start CDS again and it will go on as if nothing has
happened. Any selection screens are skipped and CDS
will go on with the next volume in the list. If this
is NOT what you want, you can supply /NORESTART and
CDS will start from scratch again. If you did finish
CDS in a NORMAL way (not pressing ESC), the restart
files are scratched and CDS will start from scratch
the next time. You can also force CDS to start from
scratch (after abnormal termination) by deleting the
files CDS$$???.??? from disk;
4.7 CDT
────────────────────────────────────────────────────────────────────────
This is a nice utility if you get ALLFILES listings that will be used
to add comments to your CATDISK <tm> database(s). It needs the CDU.CTL
or CDT.CTL file to do its work (FilelistUpdate and GlobalChange
options in one or both of these files).
CDT is called with the following syntax:
CDT [file] {/MANUAL}
[file] Must be the complete filename (optionally you can add
the path and drive but the complete name can not be
longer than 40 bytes) of the comment-file that
contains the comments that must be imported;
/BASELOC=lllll This option can overrule the location of the CATDISK
databases that was set with either the CATBASE env.
ver. or the CDUCATDISKBASE option in the CDU.CTL (or
alike) files.
/MANUAL Normally CDT will start an automatic sequence to pass
the actions to CATDISK <tm>. This will work only
partial when you run a non-registered version of
CATDISK <tm>. In this case you can (must) add /MANUAL
to the command-line. The CDT program will NOT pass
the /CATALOG, /QUIET, /NOSHELL, /NP, /NW, /NT and /NS
command-line options to CATDISK <tm>, so you are on
your own when CATDISK <tm> is called;
The normal rules for the text-files apply. CATDISK can only use the
first 32767 lines. The file must be a text-file (no tabs and lines not
longer than 255 bytes). CDT will NOT read (and/or process) the
text-file itself in any way. It will only parse the CDU.CTL file and
will supply the correct calls to CATDISK. If you are running a
non-registered CATDISK <tm>, you must use the following sequence after
CATDISK <tm> is called by CDT:
- Pass the intro-screen;
- Press <9>;
- Press <F10>;
- Press <ESC> a couple of times (CDT will flush the keyboard after
CATDISK <tm> exits back to CDT;
Registered CATDISK <tm> users can sit back and relax (why shouldn't
YOU register CATDISK and CDU ?). Some examples (CDT.CTL, CDT.EX1 and
CDT.EX2 are supplied inside the archive CDT__EXA.???).
│4.8 CDZ
│────────────────────────────────────────────────────────────────────────
│CDZ makes CATDISK <tm> even more useful. Until now, CATDISK <tm>
│could store information of any logical drive (diskette, hardisk,
│whatever has a drive-letter) but with help of the CDZ utility, you can
│also access your TAPE device. The 2.01 version of CDZ (the first) is a
│somewhat 'rudimentary' version in the way that it only supports the CMS
│(Colorado Memory Systems) JUMBO 120 and JUMBO 250 tape-drives. The
│majority of non-commercial setups use such a tape-drive though.
│Anyway, make sure to read the included HELPTAPE.ME! file !
│
│What CDZ does, is, with help of the CMS TAPE.EXE (Jumbo version 3.03),
│obtain the information from your tapes and convert this information
│into CATDISK databases which can be accessed thru CATDISK <tm> !
│
│CDZ is called with the following syntax:
│
│CDZ {/BASE=nnnn} {/BASELOC=llll} {/NOFILES} {/TAPENAME=vvvv}
│ {/TAPECOMM=cccc}
│
│/BASE=nnnnnnnn the same as with CDC (see documentation on CDC above)
│
│/BASELOC=lllll This option can overrule the location of the
│ CATDISK databases that was set with either the
│ CATBASE env. ver. or the CDUCATDISKBASE option in
│ the CDU.CTL (or alike) files.
│
│/NOFILES Normally CDZ will obtain all information from the
│ tape in question. All information means:
│
│ - All volumes on the tape (and their description)
│
│ - All files inside all volumes (when they are
│ compatible with the QIC-40/80 backup strategy)
│
│ This process can take very long (up to 15 to 20 min.
│ per tape, mostly because TAPE.EXE takes very long to
│ initialize the tape-drive and ALL volumes need to be
│ listed in sequential order).
│
│ When you specify /NOFILES, CDZ will only obtain all
│ volume-related information from the tape (see 4.9 for
│ a description of volumes, files and tapes) and will
│ skip the search for files inside the volumes. This
│ causes TAPE.EXE only to be executed once for every
│ tape, thus taking between 1 and 3 minutes for each
│ tape. The information inside the CATDISK database
│ will contain all volumes AND THEIR DESCRIPTION (the
│ most important).
│
│/TAPENAME=vvvv You can run CDZ unattended. Normally CDZ will need to
│ know the name of the tape (this can not be obtained
│ thru TAPE.EXE when called from a program) which must
│ be entered manually. You can skip the manual answer
│ when you supply the name of the tape 'vvvvv' with the
│ TAPENAME command-line option. Any spaces must be
│ coded as underscore ('_') characters and the
│ tape-name must be 1 to 11 positions. For example:
│
│ /TAPENAME=TAPE_001
│
│ Will skip the question in CDZ and catalog the current
│ tape as 'TAPE 001' in the database. To run fully
│ unattended, you also need to supply /BASE on the
│ command-line when you use more than one database.
│
│/TAPECOMM=vvvv As with /TAPENAME, this option is meant to be used as
│ an option to run unattended. You can supply the new
│ summary comment for the tape to be processed. This is
│ a new option in CATDISK <tm> version 7.0 ! If you are
│ RECATALOGING a tape and the old tape in the database
│ already had a summary comment, that comment will be
│ used and the comment on /TAPECOMM will be ignored. Any
│ spaces must be coded as an underscore. For example:
│
│ /TAPECOMM=A_backup_tape
│
│
│Check out chapter 4.9 for odds and pieces about tape-support. The way
│CDZ detects errors on the tape-drive is very rudimentary. If an error
│occurs, the error will be routed to CDZ and CDZ will report the error.
│If there is already data obtained from the tape, the database will be
│updated (even with the error). If there wasn't any data (f.i. when the
│tape was not mounted), the database will not be updated and the
│previous status will still apply !
│
│
│4.9 Notes on tape support
│────────────────────────────────────────────────────────────────────────
│CDZ can access the tape-drive thru the CMS TAPE.EXE utility. Up to
│now, CDZ could only be tested with release 3.03 of the CMS software
│(Jumbo version). If you have a different release, you can *try* to use
│that version, but make sure to create an empty database with CATDISK
│itself and use that base for testing. I would like to know if other
│versions work.
│
│The same goes for CMS software for other types of tape-drives like
│parallel drivers and the Tracker <tm>. See HELPTAPE.ME! for more info
│on this subject !
│
│On one TAPE (DC2000/DC2120), there can be one or more VOLUMES. Each
│VOLUME can have one or more FILES inside. When you create a backup
│with TAPE.EXE, CPBACKUP (QIC-40/80 compatible format) or NBACKUP (2.0
│or 2.2), one or two VOLUMES are written for every backup (the second
│could be a copy of the backup-catalog).
│
│CDZ will maintain CATDISK COMPATIBLE databases (the SUM and DTA
│files). They are NOT CATDISK databases but merely databases that are
│compatible with CATDISK. The initial database (the first, empty
│database for your tapes) must be created with CATDISK.EXE though !
│
│CDZ will obtain all information about VOLUMES. Normally there is a
│comment attached to the VOLUME (like FF83950A.FUL, A Norton Backup
│Catalog or something else). A VOLUME is stored inside a CATDISK <tm>
│COMPATIBLE database as a file, belonging to the tape (like a file
│belonging to a diskette). The actual volumes don't have logical names
│but will be stored as filenames VOL__xxx.TAP (where xxx is the xxxth
│volume on that TAPE). The decription will tell the actual contense of
│that VOLUME.
│
│CDZ will also obtain all information about FILES inside VOLUMES (when
│you did not supply /NOFILES and the VOLUME is QIC-40/80 compatible and
│compatible with CMS TAPE.EXE). CDZ will store each FILE inside a tape
│VOLUME in a CATDISK <tm> COMPATIBLE database as a file (*LBR type)
│belonging to an archive. The archive is the main-filename (e.g. the
│tape-volume, e.g. VOL__xxx.TAP) and all files inside the VOLUME will
│be chained to VOL__xxx.TAP. I have used the *LBR (LU/LIBRARY)
│attribute inside the CATDISK structure because it is not frequently
│used but still available (a new attribute for tapes, Rick ??).
│
│If the VOLUME seems not to contain files inside, it will probably not
│be compatible with TAPE.EXE.
│
│CDZ does create and update the CATDISK database in a different way as
│CATDISK <tm> itself does. It is advised to use separate databases for
│diskettes and tapes. First because they don't mix that well and
│secondly, when I have made logical errors in the way I maintain the
│database, you must blame me and not the author of CATDISK. In fact,
│CDZ creates/updates a DTA/SUM file by itself and the internals of
│these files happen to be the same as the DTA/SUM files that CATDISK
│itself maintains. That is why you can use CATDISK to view these files
│and create reports ! You can also remove entries and do other things
│with them, like changing the comments ! Again, when you have any
│problems with CATDISK <tm> and the DTA/SUM files created by me, don't
│blame the author of CATDISK. Also don't blame me, there is NO guaranty
│that it works !!
│
│In version 2.01 there is NO check that the DTA/SUM files get to big.
│If they are, they are not anymore compatible with CATDISK but can
│still be listed with CDF.EXE ! To keep them compatible, I advise you
│to check for the number of files and volumes on a regular basis. In a
│next version, I will do the checks myself (when CDZ seems useful to
│you all).
┌───────┬─────────────────────────────────────────────────────────────┐
│ 5 │ Version information and credits │
└───────┴─────────────────────────────────────────────────────────────┘
5.1 The BETA-team
────────────────────────────────────────────────────────────────────────
Look into the file SUPPORT.CDU for a full list of all beta-testers.
5.2 Credits
────────────────────────────────────────────────────────────────────────
Thanks to the following people:
- Rick Hillier for CATDISK <tm>;
- The BETA-team (a very warm and loud applause !);
5.3 Version history
────────────────────────────────────────────────────────────────────────
┌───────┬────────────────────────────┐
│ 1.01 │ First rudimentary release │
└───────┴────────────────────────────┘
■ Try it out
┌───────┬────────────────────────────┐
│ 1.02 │ Bug release (only CDD) │
└───────┴────────────────────────────┘
CDC
■ Nothing changed, not supplied in 1.02
CDD
■ CDD would incorrect detect files that were to old. Newer files were
not deleted but some of the older files could stay on the diskette
library. This is fixed;
■ CDD first sort out the possible deletes. Then CDD would ask for
volumes and at THIS moment the user could reply Y/N. This order is
changed. CDD will sort out the matches and will ask a Y/N before
ANY volume has to be mounted;
CDF
■ Nothing changed, not supplied in 1.02
CDM
■ Nothing changed, not supplied in 1.02
CDS
■ Nothing changed, not supplied in 1.02
┌───────┬────────────────────────────┐
│ 1.03 │ Minor release │
└───────┴────────────────────────────┘
CDC
■ Only some cosmetic changes;
CDD
■ Added /RESTART;
■ Added /NOSTUFFKEY to overrule the stuffing of keys into the
keyboard to run CATDISK <tm> almost unattended;
■ Added option to 'Q'uit the selection process. CDD will start with
the files you selected so far. Hitting [ESC] in the questionaire
will cause CDD to terminate;
■ Some cosmetic changes
CDF
■ Some cosmetic changes;
■ A mask is not needed anymore when you use /FREE;
CDM
■ Added /RESTART;
■ Added /NOSTUFFKEY to overrule the stuffing of keys into the
keyboard to run CATDISK <tm> almost unattended;
■ Some cosmetic changes
CDS
■ Some cosmetic changes
┌───────┬────────────────────────────┐
│ 1.10 │ Minor release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Changed some cosmetics;
┌─────┐
│ CDR │
└─────┘
■ Changed the name from CDD.EXE into CDR.EXE;
■ Changed the parsing routines for labels on diskette a bit. This
should fix problems with labels containing binary zeroes. Also all
labels are looked at in uppercase manner;
■ Fixed a problem where CDR would display invalid dates on the
selection screen;
■ Added support for CATDISK 6.xx (other stuffed keys). Old CATDISK
releases are still supported with the /CDISK4 command-line option;
■ Added support for user-switches, normally used with CATDISK, by
looking for the environment variable CATPARM;
■ Recoded the restart procedures, removed the /RESTART option and
added the /NORESTART option to switch automatic restart off;
┌─────┐
│ CDF │
└─────┘
■ Some cosmetic changes;
■ A mask is not needed anymore when you use /FREE;
┌─────┐
│ CDM │
└─────┘
■ Changed the parsing routines for labels on diskette a bit. This
should fix problems with labels containing binary zeroes. Also all
labels are looked at in uppercase manner;
■ Added support for CATDISK 6.xx (other stuffed keys). Old CATDISK
releases are still supported with the /CDISK4 command-line option;
■ Added support for user-switches, normally used with CATDISK, by
looking for the environment variable CATPARM;
■ Recoded the restart procedures, removed the /RESTART option and
added the /NORESTART option to switch automatic restart off;
┌─────┐
│ CDS │
└─────┘
■ Changed the parsing routines for labels on diskette a bit. This
should fix problems with labels containing binary zeroes. Also all
labels are looked at in uppercase manner;
■ Changed the layout a bit. It now looks more the same as CDM and
CDR;
■ Added support for CATDISK 6.xx (other stuffed keys). Old CATDISK
releases are still supported with the /CDISK4 command-line option;
■ Added a restart procedures in the same manner as CDM and CDR. Added
the /RESTART option to the program;
┌───────┬────────────────────────────┐
│ 1.15 │ Minor & bug release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Changed some internal routines a bit;
┌─────┐
│ CDR │
└─────┘
■ Fixed a serious bug in the parsing of volume-labels. This caused
CDR NOT to recognize some (or all) diskettes. This is fixed;
■ CDR did recognize the /CDISK4 command-line parameter but forgot to
do something with it. This is fixed;
■ CDR will now look if there is a CATDISK env.var. available and will
use the values;
■ CDR will now work with registered versions of CATDISK <tm>;
┌─────┐
│ CDF │
└─────┘
■ Nothing changed;
┌─────┐
│ CDM │
└─────┘
■ Fixed a serious bug in the parsing of volume-labels. This caused
CDM NOT to recognize some (or all) diskettes. This is fixed;
■ CDM will now look if there is a CATDISK env.var. available and will
use the values;
■ CDM will now work with registered versions of CATDISK <tm>;
■ Changed the algorithm for duplicate files. You can now make three
different choices. Either you remove the file from the hard-disk,
you add the new file to diskette (so both will exist on diskette)
or you can remove the version on diskette and add the one on hard-
disk to diskette (Y,N or A);
┌─────┐
│ CDS │
└─────┘
■ Fixed a serious bug in the parsing of volume-labels. This caused
CDM NOT to recognize some (or all) diskettes. This is fixed;
┌───────┬────────────────────────────┐
│ 1.20 │ Minor & bug release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Changed to the new CATDISK <tm> 6.30 record-layout;
┌─────┐
│ CDF │
└─────┘
■ Changed to the new CATDISK <tm> 6.30 record-layout;
┌─────┐
│ CDM │
└─────┘
■ Changed to the new CATDISK <tm> 6.30 record-layout;
■ Removed the /CDISK4 and /NOSTUFFKEY options;
■ Added the /MANUAL option;
■ The drive (/DRIVE=d) was NOT passed to CATDISK <tm>, causing this
program to use the installed drive. This is fixed;
┌─────┐
│ CDR │
└─────┘
■ Changed to the new CATDISK <tm> 6.30 record-layout;
■ Removed the /CDISK4 and /NOSTUFFKEY options;
■ Added the /MANUAL option;
■ The drive (/DRIVE=d) was NOT passed to CATDISK <tm>, causing this
program to use the installed drive. This is fixed;
┌─────┐
│ CDS │
└─────┘
■ Changed to the new CATDISK <tm> 6.30 record-layout;
┌─────┐
│ CDT │
└─────┘
■ New program;
┌───────┬────────────────────────────┐
│ 1.25 │ Major release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Some internal changes;
■ Added coding to work with the new GLOBAL options CDUTempDirectory
and CDUSwapDirectory (see documentation);
┌─────┐
│ CDF │
└─────┘
■ CDF was getting to big. You can now select up to 20000 files in one
turn (was 30000);
■ Added coding to work with the new GLOBAL options CDUTempDirectory
and CDUSwapDirectory (see documentation);
┌─────┐
│ CDM │
└─────┘
■ Fixed a problem where lost clusters would occur when you terminated
CDM before any diskette was written;
■ Sometimes CDM is unable to move a file to diskette because you have
done some manipulations on the diskette (added new files) without
updating this diskette in the CATDISK <tm> database. In this case,
CDM would leave the file as-as (this is still the case) and you had
to remember to update the diskette yourself. This is changed in way
that the program now calls CATDISK <tm>, even when there is an
error on the diskette, so CATDISK <tm> will update the new status
at once;
■ When a volume is wrong, CDM would return the same question. Now CDM
will also show WHICH volumeID is in the diskette-drive OR will show
I/O error when there isn't a diskette in the drive at all;
■ Added coding to work with the new GLOBAL options CDUTempDirectory
and CDUSwapDirectory (see documentation);
■ The answer you supply is now displayed in caps-on and in a
different color in the menu;
■ Added the Directory2Base option to automate much of CDM's operation
(no questions for base and diskette-drive letter when option is
supplied);
┌─────┐
│ CDR │
└─────┘
■ Fixed a problem where lost clusters would occur when you terminated
CDM before any diskette was written;
■ Added the ToOldFiles option for CDU.CTL. Can be overruled with the
/TOOLD= command-line switch or switched off with the /TOOLD=-
command-line option;
■ Added the /TOOLD=-mm command-line option;
■ Added the /TOOLD=- command-line option;
■ The answer you supply is now displayed in caps-on and in a
different color in the menu;
■ When a volume is wrong, CDM would return the same question. Now CDM
will also show WHICH volumeID is in the diskette-drive OR will show
I/O error when there isn't a diskette in the drive at all;
┌─────┐
│ CDS │
└─────┘
■ Fixed a problem where lost clusters would occur when you terminated
CDM before any diskette was written;
■ Fixed a bug where the FILES.BBS did contain 1 space to many. The
format is now changed to 'ffffffff.xxx ccccccc' (so one space after
a full filename). Comment will start on position 14;
■ CDS displayed that it could work with a [mask] when you used /?.
This did not work at all (CDS showed ALL files in age-descending
order). Now you can supply up to 50 masks to limit the selection to
specific files (they are still reported in age-descending order);
■ The answer you supply is now displayed in caps-on and in a
different color in the menu;
■ When a volume is wrong, CDM would return the same question. Now CDM
will also show WHICH volumeID is in the diskette-drive OR will show
I/O error when there isn't a diskette in the drive at all;
■ Added /DEL command-line option. In this case CDS will not COPY the
file(s) but will MOVE them (COPY + DELETE) from the diskettes. In
this case CATDISK <tm> itself is called to update the diskette in
the correct database;
┌─────┐
│ CDT │
└─────┘
■ The old format (with the CDT.CTL file) is now obsolete. The
complete CDU package can now use CDU.CTL (or a specific CDT.CTL)
and all options have been changed somewhat. This means that the
array of comment-files are now translated to separate options which
are called FileListUpdate. Take a good look at the documentation
(3.1 and 3.3.6) !
┌───────┬────────────────────────────┐
│ 1.26 │ Bug-fix release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDC.CTL);
┌─────┐
│ CDF │
└─────┘
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDF.CTL);
┌─────┐
│ CDM │
└─────┘
■ Fixed a bug where the restart would not find the previous files.
Unless CDM did write the temporary files in the 'current' directory
there would never be a restart !
■ Fixed a cosmetic bug where y/n/a (when 'a' was your choice) would
display as y/n/N and not as y/n/A (last character highlighted). This
is fixed;
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDM.CTL);
┌─────┐
│ CDR │
└─────┘
■ Fixed a bug where the restart would not find the previous files.
Unless CDR did write the temporary files in the 'current' directory
there would never be a restart !
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDR.CTL);
┌─────┐
│ CDS │
└─────┘
■ Fixed a bug where the restart would not find the previous files.
Unless CDS did write the temporary files in the 'current' directory
there would never be a restart !
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDS.CTL);
┌─────┐
│ CDT │
└─────┘
■ Added the /BASELOC command-line parameter;
■ Added support for the new CDUCATDISKBASE and CDUCATDISKPROG options
in CDU.CTL (CDT.CTL);
┌───────┬────────────────────────────┐
│ 1.30 │ Minor release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Nothing changed.
┌─────┐
│ CDF │
└─────┘
■ CDF is now able to search for the supplied file-masks in ALL the
available databases which are in the installed directory. When /ALL
is added to the command-line, CDF will perform this multi-database
selection;
■ CDF has now several sort options to sort on date (/SD), size (/SS),
VolumeID (/SV) and archive (/SA);
■ CDF can now display up to 40 bytes of each comment. You can use the
CRSR-LEFT and CRSR-RIGHT multiple times to scroll thru the info;
┌─────┐
│ CDM │
└─────┘
■ Nothing changed.
┌─────┐
│ CDR │
└─────┘
■ Nothing changed.
┌─────┐
│ CDS │
└─────┘
■ Nothing changed.
┌─────┐
│ CDT │
└─────┘
■ Fixed bugs which caused CDT to abort on the CDUCATDISKBASE and
CDUCATDISKPROG options in CDT.CTL or CDU.CTL;
■ CDT will now always copy the original file to a temporary file, even
when NO GlobalChange options are set;
■ CDT will split the commet-file into two or more portions when the
number of records inside the comment-file is higher than 32767;
┌───────┬────────────────────────────┐
│ 1.31 │ Minor release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Nothing changed.
┌─────┐
│ CDF │
└─────┘
■ Changes some internal routines to overcome possible errors;
┌─────┐
│ CDM │
└─────┘
■ Fixed problem with the cluster-sizes for high density diskettes.
In some cases these diskettes would be marked as full when still
512 bytes were available;
■ Added CLUSTERSIZE option to set the cluster-size for special formats
like 1.6 Mb with clusters of 2048 bytes;
┌─────┐
│ CDR │
└─────┘
■ Nothing changed.
┌─────┐
│ CDS │
└─────┘
■ Nothing changed.
┌─────┐
│ CDT │
└─────┘
■ Nothing changed.
┌───────┬────────────────────────────┐
│ 1.32 │ Bug fix release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Nothing changed.
┌─────┐
│ CDF │
└─────┘
■ Fixed a problem where CDF could not find ANY CATDISK file that had a
total length of 9 bytes or more (ARCH.DTA was valid but CATDISK.DTA
was displayed but would not be processed);
┌─────┐
│ CDM │
└─────┘
■ Nothing changed.
┌─────┐
│ CDR │
└─────┘
■ Nothing changed.
┌─────┐
│ CDS │
└─────┘
■ Nothing changed.
┌─────┐
│ CDT │
└─────┘
■ Nothing changed.
┌───────┬────────────────────────────┐
│ 2.01 │ Major Release │
└───────┴────────────────────────────┘
┌─────┐
│ CDC │
└─────┘
■ Replaced some buggy routines;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
┌─────┐
│ CDF │
└─────┘
■ Replaced a routine which could (under rare conditions) cause a
hangup;
■ Fixed a problem with very big file-sizes and disk-sizes which caused
CDF to screwup the screen. Also with CDZ (tape-support) in mind, a
longer field would be nice. When the file-size is 10 MB or more,
CDF will now display the value in MB;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
┌─────┐
│ CDM │
└─────┘
■ Replaced a routine which could (under rare conditions) cause a
hangup;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
■ Added the support for the BASEOPTIONS and BASEDRIVE options in the
CDx.CTL file (see documentation);
■ Fixed a problem where CDM would show an empty entry on the list of
diskette volumes when there were more files to copy than there was
room on all the diskettes;
■ CDM will now also show the NEXT diskette to mount when the request
for the current diskette is displayed;
■ Added the option to supply the directory, on which CDM has to work
on, on the command-line. CDM will still try to match this directory
with one of the DIRECTORY2BASE options in CDx.CTL (if any);
┌─────┐
│ CDR │
└─────┘
■ Replaced a routine which could (under rare conditions) cause a
hangup;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
■ Added the support for the BASEOPTIONS and BASEDRIVE options in the
CDx.CTL file (see documentation);
■ CDR will now also show the NEXT diskette to mount when the request
for the current diskette is displayed;
■ Added the EXCLUDEFILE option to make it possible to exclude one or
more files from removal, even when they match the criteria (on date
and/or filemask);
┌─────┐
│ CDS │
└─────┘
■ Replaced a routine which could (under rare conditions) cause a
hangup;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
■ Added the support for the BASEOPTIONS and BASEDRIVE options in the
CDx.CTL file (see documentation);
■ CDS will now also show the NEXT diskette to mount when the request
for the current diskette is displayed;
┌─────┐
│ CDT │
└─────┘
■ Replaced a routine which could (under rare conditions) cause a
hangup;
■ Fixed some coding to make the names of the temporary files more
consistent with all other CDU programs;
┌─────┐
│ CDZ │
└─────┘
■ This program (tape catalogging in a CATDISK <tm> database) is now
added to the set of CDU utilities !
┌───────┬────────────────────────────┐
│ 2.10 │ Minor Release │
└───────┴────────────────────────────┘
■ All programs changed to the new CATDISK <tm> 7.00 release. You can
NOT use this version with CATDISK 6.3x. Use CDU 2.01 instead when
you are still using CATDISK 6.30 to 6.37, better, upgrade to the
new CATDISK 7.00 !
5.4 Copyright, Trademarks
────────────────────────────────────────────────────────────────────────
CATDISK is a trademark of Rick Hillier
NBackup and
│Norton are trademarks of Symanec Coorporation
│CPBackup is a trademark of Central Point Software Inc.
4Dos is a trademark of J.P. Software / R.C. Conn and T. Rawson
Stacker is a trademark of Stac Electronics, Carlsbad
Diet is a trademark of Teddy Matsumoto
Doublespace is a trademark of Microsoft
│CMS, Jumbo
│and Tracker are trademarks of Colorado Memory Systems
│
│CDU is written in Borland Pascal 7.0, with help of the Turbo Debugger
│3.0 and makes extensive use of Object Professional 1.20.
Borland Pascal is a trademark of Borland International
Turbo Debugger is a trademark of Borland International
Object Professional is a trademark of TurboPower Inc.
==================== END OF DOCUMENT ==================================